With bug 1004678 fixed, we'll be able to add "break on mutation" options to the inspector's markup-view. Bug 1004678 is about making this possible at debugger level, and this bug should be about 2 things: - adding the necessary UI to the markup-view (firebug does this within the context menu that appears when right-clicking on a node, see https://dl.dropboxusercontent.com/u/714210/firebug-break-on-mutation.png), - starting the debugger in the background when a "break on mutation" option is chosen, and switching to the debugger panel in the toolbox when the code is paused.

Regarding the additional UI in the markup view, it would be nice if the element that had this state applied had some visual indication beyond a checked item in the context menu. Maybe a small icon next to the item in the tree, or some kind of border to call out elements with the behavior active.

(In reply to Brian Grinstead [:bgrins] from comment #1) > Regarding the additional UI in the markup view, it would be nice if the > element that had this state applied had some visual indication beyond a > checked item in the context menu. Maybe a small icon next to the item in > the tree, or some kind of border to call out elements with the behavior > active. Another idea for the UI would be to show a breakpoint icon next to the element in the markup view, same as the icon you see when clicking in a gutter on script in the debugger

(Enhancing summary because I couldn't find this bug earlier..)

Assigning P1 priority for some devedition-40 bugs. Filter on '148DD49E-D162-440B-AE28-E22632FC20AC'

Filter on CLIMBING SHOES